home *** CD-ROM | disk | FTP | other *** search
- Path: newshost.lanl.gov!tanmoy
- From: tanmoy@qcd.lanl.gov (Tanmoy Bhattacharya)
- Newsgroups: comp.lang.c
- Subject: Re: Standard question - pointer initialization
- Date: 15 Mar 1996 22:32:47 GMT
- Organization: Los Alamos National Laboratory
- Message-ID: <TANMOY.96Mar15153247@qcd.lanl.gov>
- References: <4hk9un$906@hammer.msfc.nasa.gov> <4i52bk$5el@s02.pavilion.co.uk>
- <TANMOY.96Mar12211525@qcd.lanl.gov>
- <1996Mar14.113012.7984@friend.kastle.com>
- NNTP-Posting-Host: qcd.lanl.gov
- Mime-Version: 1.0
- Content-Type: text
- In-reply-to: rich@kastle.com's message of Thu, 14 Mar 1996 11:29:28 GMT
-
- In article <1996Mar14.113012.7984@friend.kastle.com>
- rich@kastle.com (Richard Krehbiel) writes:
- <snip>
- RK:
- RK: C not only lets you write really portable stuff, it also lets you
- RK: write really platform/compiler/vendor-specific stuff, and that's a
- RK: GOOD thing.
- RK:
-
- I agree, except at that point I stop calling it C :-)
-
- More importantly, most often people write non-portable code where
- portable code would be as good. Having ported code which was never
- meant to be ported I think that is a chain of thought which ought to
- be stamped out; and I for one will attempt to do so.
-
- Basically, there are four reasons why people write non-portable code:
-
- 1) Ignorance
- 2) Laziness
- 3) Efficiency
- 4) Platform specific stuff.
-
- I accept only 3) and 4) as valid reasons.
-
- Cheers
- Tanmoy
- --
- tanmoy@qcd.lanl.gov(128.165.23.46) DECNET: BETA::"tanmoy@lanl.gov"(1.218=1242)
- Tanmoy Bhattacharya O:T-8(MS B285)LANL,NM87545 H:#9,3000,Trinity Drive,NM87544
- Others see <gopher://yaleinfo.yale.edu:7700/00/Internet-People/internet-mail>,
- <http://alpha.acast.nova.edu/cgi-bin/inmgq.pl>or<ftp://csd4.csd.uwm.edu/pub/
- internetwork-mail-guide>. -- <http://nqcd.lanl.gov/people/tanmoy/tanmoy.html>
- fax: 1 (505) 665 3003 voice: 1 (505) 665 4733 [ Home: 1 (505) 662 5596 ]
-